Skip to content

POC: Copilot CLI extension to simplify RPI agentic development workflow#16228

Draft
JennyPng wants to merge 21 commits into
Azure:mainfrom
JennyPng:copilot-sdk-experiment
Draft

POC: Copilot CLI extension to simplify RPI agentic development workflow#16228
JennyPng wants to merge 21 commits into
Azure:mainfrom
JennyPng:copilot-sdk-experiment

Conversation

@JennyPng

@JennyPng JennyPng commented Jul 1, 2026

Copy link
Copy Markdown
Member
  • read README.md for how to use. TLDR check out this branch, install the extension, symlink if you want to access it in any repo otherwise it only works in this repo

  • automates the research->plan->implement workflow with a Copilot CLI extension, allowing you to manage phases of the workflow with slash commands like rpi-start , rpi-continue, etc. - even rpi-auto to run through the entire RPI automatically

  • toggling rpi-autojudge enables each stage to auto-run rubberduck afterwards

  • requires copilot CLI to be on experimental mode

image
  • writes artifacts to a gitignored dir
image

@@ -0,0 +1,100 @@
# Phase 2 — Assumptions (read-only)

You are in the **assumptions** phase. Surface every assumption I might be making about

@l0lawrence l0lawrence Jul 2, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⁠for /rubber-duck could you pull that command into this skill to get it to help identify assumptions or is the assumption portion supposed to be conducted by the same LLM and then you rubber duck later (or separately)?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so since CLI extension only works within the same Copilot session, I couldn't achieve the full clean context between stages. So this entire flow is orchestrated by an agent in the same session, but the extension can run /compact between stages which I think achieves a similar effect

but I do have a 'rpi-judge' command that will run rubber duck, and a command like rpi-autojudge where if you run that, and then start this flow, then every single stage in this flow will have rubber duck run after the artifact is generated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh that would be so helpful

@JennyPng JennyPng Jul 7, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

edit: i found out you can actually spawn subagents on demand, it's just experimental but i added that as an option too that you can toggle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants